home *** CD-ROM | disk | FTP | other *** search
- Path: alpha.ru.ac.za!cspw
- From: cspw@cs.ru.ac.za (Peter Wentworth)
- Newsgroups: comp.lang.c++
- Subject: Re: Visual Basic vs. Visual C++
- Date: 1 Jan 96 08:44:09 GMT
- Organization: Computer Science Department, Rhodes University
- Message-ID: <cspw.820485849@alpha>
- References: <4bu9ut$6j7@news-srv1.fmr.com>
- NNTP-Posting-Host: alpha.ru.ac.za
- NNTP-Posting-User: cspw
- X-Newsreader: NN version 6.5.0 (NOV)
-
- In <4bu9ut$6j7@news-srv1.fmr.com> David Button <David.Button@fmr.com> writes:
-
- I think you need to weigh the relative importances of the speed of
- the application with your aggressive time frames. Interpreted languages
- are slower, but the overhead price tends to become negligible
- *if* the hard-coded primitives constitute the bulk of the work.
- If you're into serious number crunching, sorting, searching,
- or moving graphics about, etc., you'll have to have primitives or
- DLL's (written in C++ or something) for those aspects.
-
- VB is currently (IMO) a cleaner language: you're isolated from the
- "assembly level windows API", and won't have to ever see or even
- know about windows handles, graphics contexts, etc. But as another
- respondent pointed out, if you want to work at the higher level then
- you pay the price of living within the constraints and design framework
- which it provides. If at heart you believe that *real programmers*
- write assembler, then Visual C++ will get you right into the mud
- of the Windows API.
-
- In some senses, I reckon VB is perhaps a better "glue" for sticking
- together existing components. VC++ is the better tool if most of
- the development is going to be creating new components.
-
- I think you could work on more aggressive schedules with VB, but
- you'd probably end up with some compromises in your design, and
- a speed disadvantage which may or may not be too serious, depending
- on your ration of "glue" to "component building".
-
- You probably want to look at Delphi too, since it seems to have
- gone quite a long way towards hiding the horrors of the windows
- API and yet it has solved the two-tier problems of VB - having
- to write components in some language other than your glue language.
-
- Perhaps someone can venture some opinions about why we cannot get
- a Visual C++ that is at least as clean as Delphi?
-
- Peter
-
-
- >I know I am asking for trouble, but we are undertaking a new project
- >with a relatively agressive time frame and we're trying to decide
- >whether to program in Visual Basic or Visual C++. It is a desktop
- >application which will typically be running on 486's with 4M-8M of
- >memory. We are primarily concerned with the speed of the application
- >(both actual and perceived), availability of competent programmers,
- >and the time to develop (we are under a rather aggressive time
- >schedule). If anyone has read any helpful publications or has
- >performed/seen some benchmark applications, please respond to this
- >message. Any help you can give will be greatly appreciated.
-
- >Thanks,
- >David Button
-
-
- --
- EP Wentworth - Dept. of Comp. Sci. - Rhodes University - Grahamstown - RSA.
- cspw@cs.ru.ac.za Knuth's Caveat: "While I have informally proved it,
- fax: +27 461 311915 I haven't tested it much."
-
-